Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix MultiGPU Testing #2931

Merged
merged 1 commit into from
Aug 15, 2015
Merged

Fix MultiGPU Testing #2931

merged 1 commit into from
Aug 15, 2015

Conversation

ronghanghu
Copy link
Member

This is a patch for multi-gpu testing issue (#2926). The problem is when calling make runtest with TEST_GPUID != 0 on a MultiGPU machine, solver tests will crash because gpu ids in multi-gpu tests doesn't match that of single GPU test.

Note: this still doesn't fix the crash if you have 2 widely different device at the same time. #2926 (comment)

@ronghanghu ronghanghu force-pushed the fix-gpu-test branch 2 times, most recently from 1cb3c44 to e34c5ae Compare August 15, 2015 04:59
@ronghanghu
Copy link
Member Author

@thatguymike This should fix the original issue in #2926, although not for the case in #2926 (comment)

This is a patch for multi-gpu testing issue (BVLC#2926). The problem fixed in this
commit is that when calling make runtest with TEST_GPUID != 0 on a MultiGPU
machine, solver tests will crash because gpu ids in multi-gpu tests doesn't
match that of single GPU test.
@ronghanghu
Copy link
Member Author

Setting CUDA_VISIBLE_DEVICES may be a better idea, but I didn't figure out how to set it up automatically, to ensure Multi-GPU is tested by default on multi-gpu machines, while avoiding the crash in #2926 (comment)

ronghanghu added a commit that referenced this pull request Aug 15, 2015
@ronghanghu ronghanghu merged commit 25b4920 into BVLC:master Aug 15, 2015
@ronghanghu ronghanghu deleted the fix-gpu-test branch August 15, 2015 19:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant